Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b51cdd30b7b6f82d8f853f3642326358cfaf140d95019d024833500b556b82ed

Tx prefix hash: 53d9699d054f73664fc463ae34297c71e289f5be6112dfbc2f3bb67f3c09f12a
Tx public key: fb3c2086c3b176c03193569f9e9d953e70df39ff294fd5f23f348dbc7a09e996
Timestamp: 1736451424 Timestamp [UCT]: 2025-01-09 19:37:04 Age [y:d:h:m:s]: 00:162:10:34:47
Block: 1193801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115759 RingCT/type: yes/0
Extra: 01fb3c2086c3b176c03193569f9e9d953e70df39ff294fd5f23f348dbc7a09e996021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e53522abc68038e549ab0dc41656d7c2ff8bdf347129171cee22531251b1155d 0.600000000000 1680366 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": 1193811, "vin": [ { "gen": { "height": 1193801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e53522abc68038e549ab0dc41656d7c2ff8bdf347129171cee22531251b1155d" } } ], "extra": [ 1, 251, 60, 32, 134, 195, 177, 118, 192, 49, 147, 86, 159, 158, 157, 149, 62, 112, 223, 57, 255, 41, 79, 213, 242, 63, 52, 141, 188, 122, 9, 233, 150, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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