Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc476537d93ef246cd487c741b3576ea99ae1e95240741c839abe4e19f049eda

Tx prefix hash: 8d2ae7e2d2be5aef3b754d420f02559ce25d126d8e03c9618b6e3e3a7969b0c9
Tx public key: d62dd0fd64d3b3e568c1d9e9f4dd5aa30d1fff162cf8f70a835e773d05bcab4c
Timestamp: 1580662961 Timestamp [UCT]: 2020-02-02 17:02:41 Age [y:d:h:m:s]: 04:277:12:01:13
Block: 57170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089689 RingCT/type: yes/0
Extra: 01d62dd0fd64d3b3e568c1d9e9f4dd5aa30d1fff162cf8f70a835e773d05bcab4c02110000000149b77a3d000000000000000000

1 output(s) for total of 396.801111567000 dcy

stealth address amount amount idx
00: 01aa1d9534254c4526ac444edae641e82afa71542a08583de7e3f132286bc996 396.801111567000 105492 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": 57180, "vin": [ { "gen": { "height": 57170 } } ], "vout": [ { "amount": 396801111567, "target": { "key": "01aa1d9534254c4526ac444edae641e82afa71542a08583de7e3f132286bc996" } } ], "extra": [ 1, 214, 45, 208, 253, 100, 211, 179, 229, 104, 193, 217, 233, 244, 221, 90, 163, 13, 31, 255, 22, 44, 248, 247, 10, 131, 94, 119, 61, 5, 188, 171, 76, 2, 17, 0, 0, 0, 1, 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