Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58e9e7d2e2d16fae01d1189951a6a682dacd0a55269dcf8899681717838277a6

Tx prefix hash: ca94853b25a50cbea0f2baeffaed5fbcdbe68fba751342cef83d1d9c5b150cf2
Tx public key: 0b3d042ab81e7947be6369d1b082e66ea0936851c47a98ac362f92e074d75057
Timestamp: 1736355491 Timestamp [UCT]: 2025-01-08 16:58:11 Age [y:d:h:m:s]: 00:090:05:47:05
Block: 1193011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64268 RingCT/type: yes/0
Extra: 010b3d042ab81e7947be6369d1b082e66ea0936851c47a98ac362f92e074d7505702110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0608f8e57e5073acc0c010d622c237da95fa052ad44b7d77f7f0f060abec764 0.600000000000 1679568 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": 1193021, "vin": [ { "gen": { "height": 1193011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0608f8e57e5073acc0c010d622c237da95fa052ad44b7d77f7f0f060abec764" } } ], "extra": [ 1, 11, 61, 4, 42, 184, 30, 121, 71, 190, 99, 105, 209, 176, 130, 230, 110, 160, 147, 104, 81, 196, 122, 152, 172, 54, 47, 146, 224, 116, 215, 80, 87, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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