Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c9839abe2ae78f8ddfd6ac63e43e4f2c191e77fd3be454e41d26c4b8d0c8cd1

Tx prefix hash: 94b550575a604b2d9e9de9d45a699c2fab6654401165a4a686098742ff889f1d
Tx public key: 2bbccc60cf0514b26631e39ff66143afa404a03e0f9f14aa35721f9110eaaf89
Timestamp: 1726068485 Timestamp [UCT]: 2024-09-11 15:28:05 Age [y:d:h:m:s]: 00:119:13:17:15
Block: 1107865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85494 RingCT/type: yes/0
Extra: 012bbccc60cf0514b26631e39ff66143afa404a03e0f9f14aa35721f9110eaaf89021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af42b7f5808f58819513402657efe17e947cb9f735b794303c3e0a4eeaee421a 0.600000000000 1585560 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": 1107875, "vin": [ { "gen": { "height": 1107865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af42b7f5808f58819513402657efe17e947cb9f735b794303c3e0a4eeaee421a" } } ], "extra": [ 1, 43, 188, 204, 96, 207, 5, 20, 178, 102, 49, 227, 159, 246, 97, 67, 175, 164, 4, 160, 62, 15, 159, 20, 170, 53, 114, 31, 145, 16, 234, 175, 137, 2, 17, 0, 0, 0, 9, 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