Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 726a543a4612a4fb2b0732788e0cb88920261a115e88183b15280c61d4860054

Tx prefix hash: 548849da75c70402325fa44c315bdddcb244a174ac7560f864101508b5abf61e
Tx public key: c4df56257c7ab14d62f7de5892af908c6ca7b464e09a620b81eddd1da8b74aa0
Timestamp: 1578487619 Timestamp [UCT]: 2020-01-08 12:46:59 Age [y:d:h:m:s]: 04:302:22:18:15
Block: 41249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105794 RingCT/type: yes/0
Extra: 01c4df56257c7ab14d62f7de5892af908c6ca7b464e09a620b81eddd1da8b74aa0021100000089b221b3d1000000000000000000

1 output(s) for total of 448.049281821000 dcy

stealth address amount amount idx
00: c1da4fd926d32d397d0f263fe3546b43909aa53f8926b4939fa830e65c5a87e9 448.049281821000 73299 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": 41259, "vin": [ { "gen": { "height": 41249 } } ], "vout": [ { "amount": 448049281821, "target": { "key": "c1da4fd926d32d397d0f263fe3546b43909aa53f8926b4939fa830e65c5a87e9" } } ], "extra": [ 1, 196, 223, 86, 37, 124, 122, 177, 77, 98, 247, 222, 88, 146, 175, 144, 140, 108, 167, 180, 100, 224, 154, 98, 11, 129, 237, 221, 29, 168, 183, 74, 160, 2, 17, 0, 0, 0, 137, 178, 33, 179, 209, 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