Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2517605e42b8a1d94c44a8bd500c264a031cc08d39fa5f671436997a405f2c0

Tx prefix hash: dd54389fd15c20e3abd1ee9950a787e7b41af7c06008cfa2db5db254e3c7ee9f
Tx public key: 2c7a1b87e08e1ea6cdaf8d1628c9f2d53c4dfcec84c66a4aca20b03db41979d6
Timestamp: 1710955895 Timestamp [UCT]: 2024-03-20 17:31:35 Age [y:d:h:m:s]: 01:057:21:59:13
Block: 982597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302376 RingCT/type: yes/0
Extra: 012c7a1b87e08e1ea6cdaf8d1628c9f2d53c4dfcec84c66a4aca20b03db41979d602110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c24d7af0f0ef39d307cd25f14b8482d343bb653b57cd7dc18195ce807af6e347 0.600000000000 1442706 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": 982607, "vin": [ { "gen": { "height": 982597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c24d7af0f0ef39d307cd25f14b8482d343bb653b57cd7dc18195ce807af6e347" } } ], "extra": [ 1, 44, 122, 27, 135, 224, 142, 30, 166, 205, 175, 141, 22, 40, 201, 242, 213, 60, 77, 252, 236, 132, 198, 106, 74, 202, 32, 176, 61, 180, 25, 121, 214, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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