Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4fb0495d3225b8ea8131911757eb2907baadc0e078d629e08e292612bd7c401

Tx prefix hash: 1b1b0e8101a261c2cb015e2805b651dd9000c2ebb2097495ff6d8d9628b49d00
Tx public key: fe837933fab22e43165d60a1641d6d9bb31a02c3a44b5beb0de13e786c900823
Timestamp: 1724660473 Timestamp [UCT]: 2024-08-26 08:21:13 Age [y:d:h:m:s]: 00:234:03:23:23
Block: 1096188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167211 RingCT/type: yes/0
Extra: 01fe837933fab22e43165d60a1641d6d9bb31a02c3a44b5beb0de13e786c900823021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56f2d191e6422f91c08da9325e423e1e0b298c49dc15e431726070f23b471ac8 0.600000000000 1571375 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": 1096198, "vin": [ { "gen": { "height": 1096188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56f2d191e6422f91c08da9325e423e1e0b298c49dc15e431726070f23b471ac8" } } ], "extra": [ 1, 254, 131, 121, 51, 250, 178, 46, 67, 22, 93, 96, 161, 100, 29, 109, 155, 179, 26, 2, 195, 164, 75, 91, 235, 13, 225, 62, 120, 108, 144, 8, 35, 2, 17, 0, 0, 0, 2, 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