Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96b509ca2b976a65b72d50fbd37800073c8c6b491ec982ebe10b06e935b00ee9

Tx prefix hash: 29bac6c2367fa16e44a9f261a7b88a7a994f58e0275dc00f1b239e235088910e
Tx public key: e0e2bc26963bc3b6ef65911e220445d7cc38e685f3a1d9a1441909416c2d7f97
Timestamp: 1724062114 Timestamp [UCT]: 2024-08-19 10:08:34 Age [y:d:h:m:s]: 00:209:16:47:49
Block: 1091236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149738 RingCT/type: yes/0
Extra: 01e0e2bc26963bc3b6ef65911e220445d7cc38e685f3a1d9a1441909416c2d7f9702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd0da2144b5479591354a0f181083ae6dc6d3819218dd9413254d13481d66554 0.600000000000 1565867 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": 1091246, "vin": [ { "gen": { "height": 1091236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd0da2144b5479591354a0f181083ae6dc6d3819218dd9413254d13481d66554" } } ], "extra": [ 1, 224, 226, 188, 38, 150, 59, 195, 182, 239, 101, 145, 30, 34, 4, 69, 215, 204, 56, 230, 133, 243, 161, 217, 161, 68, 25, 9, 65, 108, 45, 127, 151, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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