Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e527f66ce88689ceadf09365da6953e74e55443d009bfbc261182f8b2b86acc

Tx prefix hash: 397dc1ad82e6e46f15f4e732bb0bc446f7c8ed0324c34cef252abc5383af7d24
Tx public key: b1eb9613ad437ef3d40c5a7495c6a161bd2dd7c9d6b1ee83c3e0278290ddb276
Timestamp: 1705452324 Timestamp [UCT]: 2024-01-17 00:45:24 Age [y:d:h:m:s]: 01:309:22:46:19
Block: 936920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480360 RingCT/type: yes/0
Extra: 01b1eb9613ad437ef3d40c5a7495c6a161bd2dd7c9d6b1ee83c3e0278290ddb27602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8613918444dc25180922de0a095cdb256d8fc4a37c5286e014e3698df143eb16 0.600000000000 1394964 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": 936930, "vin": [ { "gen": { "height": 936920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8613918444dc25180922de0a095cdb256d8fc4a37c5286e014e3698df143eb16" } } ], "extra": [ 1, 177, 235, 150, 19, 173, 67, 126, 243, 212, 12, 90, 116, 149, 198, 161, 97, 189, 45, 215, 201, 214, 177, 238, 131, 195, 224, 39, 130, 144, 221, 178, 118, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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