Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 236b36e9dbcd268c64ddb9a4fadd307a1f5a253667308cbb75e4e70db71fcb26

Tx prefix hash: 95770e143f1b710129a79fa33c2323d5ae03ff7e9eb3222c81ee94963ae4960f
Tx public key: bc5de0b2360970d9dbf3b24042e71f736c75f853cf8fd66d30ae3fdbd5754f18
Timestamp: 1710377001 Timestamp [UCT]: 2024-03-14 00:43:21 Age [y:d:h:m:s]: 01:062:08:15:14
Block: 977792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305557 RingCT/type: yes/0
Extra: 01bc5de0b2360970d9dbf3b24042e71f736c75f853cf8fd66d30ae3fdbd5754f1802110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c099ebda6a474e778ab25f28561f82eb06bfa87f709d7b663c6ca36a8431f733 0.600000000000 1437799 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": 977802, "vin": [ { "gen": { "height": 977792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c099ebda6a474e778ab25f28561f82eb06bfa87f709d7b663c6ca36a8431f733" } } ], "extra": [ 1, 188, 93, 224, 178, 54, 9, 112, 217, 219, 243, 178, 64, 66, 231, 31, 115, 108, 117, 248, 83, 207, 143, 214, 109, 48, 174, 63, 219, 213, 117, 79, 24, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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