Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 492d3e06e76c1702c9815c6e1f5f4214563f3e426ae00ecee780ed8074564658

Tx prefix hash: 91d0e8cd8301a3ae6652599d44b7a3d5d924d35d71f3187a25e2c15820b5484f
Tx public key: 5c6aaf901fff676af30e2e903b6e751323ce75214993f6df5db17faabc5b2fa2
Timestamp: 1725644464 Timestamp [UCT]: 2024-09-06 17:41:04 Age [y:d:h:m:s]: 00:258:09:02:02
Block: 1104354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184540 RingCT/type: yes/0
Extra: 015c6aaf901fff676af30e2e903b6e751323ce75214993f6df5db17faabc5b2fa202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c6dadbd6d982886c3045791e456c3a1017e2047ae0105f8bd7311c7dedb4cc3 0.600000000000 1581463 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": 1104364, "vin": [ { "gen": { "height": 1104354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c6dadbd6d982886c3045791e456c3a1017e2047ae0105f8bd7311c7dedb4cc3" } } ], "extra": [ 1, 92, 106, 175, 144, 31, 255, 103, 106, 243, 14, 46, 144, 59, 110, 117, 19, 35, 206, 117, 33, 73, 147, 246, 223, 93, 177, 127, 170, 188, 91, 47, 162, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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