Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e76e6145c4c9819aec3a1e9aae731cf46107338708d4c5ef7f3b5d75bdd4c28

Tx prefix hash: 348db2a758eca46776871a36d29a43bef174faf26ca8926c9351cdbd90ce30f2
Tx public key: 4478090a9823a290aae37ef56f9e731cc7ca96c463763f3fa8fef0d25d6fe3b9
Timestamp: 1702357311 Timestamp [UCT]: 2023-12-12 05:01:51 Age [y:d:h:m:s]: 01:193:12:47:02
Block: 911286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399318 RingCT/type: yes/0
Extra: 014478090a9823a290aae37ef56f9e731cc7ca96c463763f3fa8fef0d25d6fe3b9021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92ee46b98320234887849a66196d2ba3ea7dc09da1dfef4d8aca7893f8911b84 0.600000000000 1368467 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": 911296, "vin": [ { "gen": { "height": 911286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92ee46b98320234887849a66196d2ba3ea7dc09da1dfef4d8aca7893f8911b84" } } ], "extra": [ 1, 68, 120, 9, 10, 152, 35, 162, 144, 170, 227, 126, 245, 111, 158, 115, 28, 199, 202, 150, 196, 99, 118, 63, 63, 168, 254, 240, 210, 93, 111, 227, 185, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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