Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee1534856bd4b3259801aa04c598a4ad264d1328e5881005bc139c4b4b4fe9a0

Tx prefix hash: b95ba4b364d576824792b1b202664385580306b56a986bf26a9fe5127c520056
Tx public key: f30936cef63f37e138a381fb3f58142a4431eddc21da3ee1450f287ac0d3c1f9
Timestamp: 1583639451 Timestamp [UCT]: 2020-03-08 03:50:51 Age [y:d:h:m:s]: 04:263:20:00:46
Block: 78509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1083232 RingCT/type: yes/0
Extra: 01f30936cef63f37e138a381fb3f58142a4431eddc21da3ee1450f287ac0d3c1f902110000001c5143fba2000000000000000000

1 output(s) for total of 337.184719039000 dcy

stealth address amount amount idx
00: 4e51db3367a271934f69f0939be4a864971ca7eda1b0bf8154b5ef66b83f55f0 337.184719039000 143969 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": 78519, "vin": [ { "gen": { "height": 78509 } } ], "vout": [ { "amount": 337184719039, "target": { "key": "4e51db3367a271934f69f0939be4a864971ca7eda1b0bf8154b5ef66b83f55f0" } } ], "extra": [ 1, 243, 9, 54, 206, 246, 63, 55, 225, 56, 163, 129, 251, 63, 88, 20, 42, 68, 49, 237, 220, 33, 218, 62, 225, 69, 15, 40, 122, 192, 211, 193, 249, 2, 17, 0, 0, 0, 28, 81, 67, 251, 162, 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