Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a1916d3a3af59da13c20569c37485e70fa991408aa194a625b2a381da041596

Tx prefix hash: 64d382594081420f8f92c3e7c39e5a0b9b02520ff1cc05c4b4b674d4b3f10297
Tx public key: 54d884919494a7c8b261889b467070e23b87dfae00db663f8dd50e453a41d12e
Timestamp: 1703171997 Timestamp [UCT]: 2023-12-21 15:19:57 Age [y:d:h:m:s]: 01:177:03:43:07
Block: 918045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387687 RingCT/type: yes/0
Extra: 0154d884919494a7c8b261889b467070e23b87dfae00db663f8dd50e453a41d12e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45c72d8f598ff07ba73001da8f7706b2cb03782e2da9d4f9d5b334d62fb42b16 0.600000000000 1375681 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": 918055, "vin": [ { "gen": { "height": 918045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45c72d8f598ff07ba73001da8f7706b2cb03782e2da9d4f9d5b334d62fb42b16" } } ], "extra": [ 1, 84, 216, 132, 145, 148, 148, 167, 200, 178, 97, 136, 155, 70, 112, 112, 226, 59, 135, 223, 174, 0, 219, 102, 63, 141, 213, 14, 69, 58, 65, 209, 46, 2, 17, 0, 0, 0, 4, 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