Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9333aae77c6279fdf9e0f8d4f77d0e769cd9732a1716411a5d3e0cfc6851c88

Tx prefix hash: cddfe9b867096e55e242b49bb1d96070b19ae5ead483d4301125d4df52745856
Tx public key: b232e2d3a1664357ad2d78e8a7f58bfedef729c6b4969c6490a0986d4dbc432e
Timestamp: 1722358855 Timestamp [UCT]: 2024-07-30 17:00:55 Age [y:d:h:m:s]: 00:249:13:20:55
Block: 1077102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178271 RingCT/type: yes/0
Extra: 01b232e2d3a1664357ad2d78e8a7f58bfedef729c6b4969c6490a0986d4dbc432e021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01bc7c804b15a18240bc8fdeba24f7bc189dcfd0990fb8ed72118e3a4eea05d1 0.600000000000 1549647 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": 1077112, "vin": [ { "gen": { "height": 1077102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01bc7c804b15a18240bc8fdeba24f7bc189dcfd0990fb8ed72118e3a4eea05d1" } } ], "extra": [ 1, 178, 50, 226, 211, 161, 102, 67, 87, 173, 45, 120, 232, 167, 245, 139, 254, 222, 247, 41, 198, 180, 150, 156, 100, 144, 160, 152, 109, 77, 188, 67, 46, 2, 17, 0, 0, 0, 7, 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