Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4a6f12ed4afaa6c3f458015cecc3aef195c20252426e19f32f08542a1c91ea6

Tx prefix hash: ed863866f3f95ba0e8915b1adad0b038956d87d07c4debedf0a2d4f4239bff66
Tx public key: 1089b208353bd79f6c891fbef9802b917bc9423ff4c267fe58b4a581abc1a849
Timestamp: 1714709377 Timestamp [UCT]: 2024-05-03 04:09:37 Age [y:d:h:m:s]: 00:336:10:10:38
Block: 1013701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240479 RingCT/type: yes/0
Extra: 011089b208353bd79f6c891fbef9802b917bc9423ff4c267fe58b4a581abc1a84902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b6ecf1dbe7d5cf4bfd6821d55c5ded64f5622916c1e455f0b074358ff6d6fe6 0.600000000000 1476588 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": 1013711, "vin": [ { "gen": { "height": 1013701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b6ecf1dbe7d5cf4bfd6821d55c5ded64f5622916c1e455f0b074358ff6d6fe6" } } ], "extra": [ 1, 16, 137, 178, 8, 53, 59, 215, 159, 108, 137, 31, 190, 249, 128, 43, 145, 123, 201, 66, 63, 244, 194, 103, 254, 88, 180, 165, 129, 171, 193, 168, 73, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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