Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 636edd10137c236fedebe35c9761519c4195b1e7c986508a1e5dce22374f1b3a

Tx prefix hash: 791fcb0d64cbe8922875b7bcee6278290c2d1f460b7f8c7c10c7b111a9d01d37
Tx public key: 1f7dd43859eaefb0b4bf544186b51251c4d1e14eb29c05f241b25ebe37f7c5ab
Timestamp: 1580701584 Timestamp [UCT]: 2020-02-03 03:46:24 Age [y:d:h:m:s]: 04:325:03:56:10
Block: 57659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123667 RingCT/type: yes/0
Extra: 011f7dd43859eaefb0b4bf544186b51251c4d1e14eb29c05f241b25ebe37f7c5ab02110000000349b77a3d000000000000000000

1 output(s) for total of 395.323488741000 dcy

stealth address amount amount idx
00: 6863edbcfa44ed6cf505a1fc77bb0dc301087bb44d9d3f025668ebc1ecba1003 395.323488741000 106565 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 57669, "vin": [ { "gen": { "height": 57659 } } ], "vout": [ { "amount": 395323488741, "target": { "key": "6863edbcfa44ed6cf505a1fc77bb0dc301087bb44d9d3f025668ebc1ecba1003" } } ], "extra": [ 1, 31, 125, 212, 56, 89, 234, 239, 176, 180, 191, 84, 65, 134, 181, 18, 81, 196, 209, 225, 78, 178, 156, 5, 242, 65, 178, 94, 190, 55, 247, 197, 171, 2, 17, 0, 0, 0, 3, 73, 183, 122, 61, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8