Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59d770bfb6cdf34f081fe8c8d9d395c35c5ad4805fe2f27ad19b4c2b02542b97

Tx prefix hash: 0fb3de47268f22013108668df3fc5d6744969aeff4e4815e612f537bfa2004e5
Tx public key: c9b843f8336948a5308d13986ae852a4a978c930ef54f8ab28a8901359b91bfc
Timestamp: 1711613321 Timestamp [UCT]: 2024-03-28 08:08:41 Age [y:d:h:m:s]: 00:288:22:00:03
Block: 988037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206805 RingCT/type: yes/0
Extra: 01c9b843f8336948a5308d13986ae852a4a978c930ef54f8ab28a8901359b91bfc0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6af27a7ecd32fac1cbded4e3e92430818968c8b4df1e1fb3dc15e9c4854be090 0.600000000000 1448298 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": 988047, "vin": [ { "gen": { "height": 988037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6af27a7ecd32fac1cbded4e3e92430818968c8b4df1e1fb3dc15e9c4854be090" } } ], "extra": [ 1, 201, 184, 67, 248, 51, 105, 72, 165, 48, 141, 19, 152, 106, 232, 82, 164, 169, 120, 201, 48, 239, 84, 248, 171, 40, 168, 144, 19, 89, 185, 27, 252, 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