Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ba704d9eb624392c776554384b219f82b365b04010892b740ff9e53bea0972f

Tx prefix hash: 385dac98e8d3a38d05528d7a71ed9e8ab4408be84926e67d6f410d397c3282e0
Tx public key: 91b4ad223ce4f5ebee3f40c8db0d4eee8f8d38c2ff43487d441426173eaed648
Timestamp: 1710214927 Timestamp [UCT]: 2024-03-12 03:42:07 Age [y:d:h:m:s]: 01:022:14:27:29
Block: 976442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277121 RingCT/type: yes/0
Extra: 0191b4ad223ce4f5ebee3f40c8db0d4eee8f8d38c2ff43487d441426173eaed6480211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47af4f3602c3f4a6c25aedf7c64e5bd709d48acdc2f1d5c18ec087944ab9771e 0.600000000000 1436437 of 15

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": 976452, "vin": [ { "gen": { "height": 976442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47af4f3602c3f4a6c25aedf7c64e5bd709d48acdc2f1d5c18ec087944ab9771e" } } ], "extra": [ 1, 145, 180, 173, 34, 60, 228, 245, 235, 238, 63, 64, 200, 219, 13, 78, 238, 143, 141, 56, 194, 255, 67, 72, 125, 68, 20, 38, 23, 62, 174, 214, 72, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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