Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da051b97314257652c2802457de199d3705a620e977c8d85b4b7a76b9d46096f

Tx prefix hash: 702c678663c8e6d3ac9652d756e0c0c932b63e958736e84a0df687374236a18a
Tx public key: 6acd7f98511664e05d5d4e8b545df6ff51ae5caec70e5717c98feed077b489c1
Timestamp: 1749465085 Timestamp [UCT]: 2025-06-09 10:31:25 Age [y:d:h:m:s]: 00:162:12:40:09
Block: 1301285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113840 RingCT/type: yes/0
Extra: 016acd7f98511664e05d5d4e8b545df6ff51ae5caec70e5717c98feed077b489c102110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 681ead5339c2b2d7df63cff60fc9878aa934f397189fb10916d603fdb4fa41e8 0.600000000000 1788842 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": 1301295, "vin": [ { "gen": { "height": 1301285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "681ead5339c2b2d7df63cff60fc9878aa934f397189fb10916d603fdb4fa41e8" } } ], "extra": [ 1, 106, 205, 127, 152, 81, 22, 100, 224, 93, 93, 78, 139, 84, 93, 246, 255, 81, 174, 92, 174, 199, 14, 87, 23, 201, 143, 238, 208, 119, 180, 137, 193, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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