Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37ea1a9855f60c8c3a7bb39bc06c0bacaa0ab3ce64bc036a55347644708d4988

Tx prefix hash: bb17b3826ed1015fcc4679784bc62b8fcf4faf751bd2666ea9e31c5e0e919850
Tx public key: 606f0b25ae2cecaaf443ab8aecda06bb72e4c064b69cdc40540f7ffb4bfcb154
Timestamp: 1723380477 Timestamp [UCT]: 2024-08-11 12:47:57 Age [y:d:h:m:s]: 00:234:08:07:10
Block: 1085586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167351 RingCT/type: yes/0
Extra: 01606f0b25ae2cecaaf443ab8aecda06bb72e4c064b69cdc40540f7ffb4bfcb154021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b5d5a129a0f5487e196e4da304ef1b24a0ebed379d941dde40beb8fa55d2a6a 0.600000000000 1560173 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": 1085596, "vin": [ { "gen": { "height": 1085586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b5d5a129a0f5487e196e4da304ef1b24a0ebed379d941dde40beb8fa55d2a6a" } } ], "extra": [ 1, 96, 111, 11, 37, 174, 44, 236, 170, 244, 67, 171, 138, 236, 218, 6, 187, 114, 228, 192, 100, 182, 156, 220, 64, 84, 15, 127, 251, 75, 252, 177, 84, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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