Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a620471725abbc0867d54981206c8b42210ea9a19c6046a38d4355084fd130

Tx prefix hash: d7712a9f9d52b895a0dd43e5d2e7d76c8708dccbf892da6449adaeb98ad1b746
Tx public key: 8cb736a4c4a4bbedc20f660950ecd0d27ff1a7287a16ca2a09695da4cbb8d5fc
Timestamp: 1706476111 Timestamp [UCT]: 2024-01-28 21:08:31 Age [y:d:h:m:s]: 01:066:04:34:28
Block: 945414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308380 RingCT/type: yes/0
Extra: 018cb736a4c4a4bbedc20f660950ecd0d27ff1a7287a16ca2a09695da4cbb8d5fc02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88d46d41aca54eac1da452d231a6e0dba271c814cf533e464a5b569f4e1bb084 0.600000000000 1403728 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": 945424, "vin": [ { "gen": { "height": 945414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88d46d41aca54eac1da452d231a6e0dba271c814cf533e464a5b569f4e1bb084" } } ], "extra": [ 1, 140, 183, 54, 164, 196, 164, 187, 237, 194, 15, 102, 9, 80, 236, 208, 210, 127, 241, 167, 40, 122, 22, 202, 42, 9, 105, 93, 164, 203, 184, 213, 252, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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