Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a4cbbff943b18ea968a3650c20e6ebda19268b3c2d7d7bf00a39f0de9df7974

Tx prefix hash: 1391e7734124da09c0082dd203d7bb7130e22d6240d7337a1442b9682d7ab518
Tx public key: 679e2201f1f7ae71b56d4874e4b188001e1f8c7ca89ddcc316653c07a1583e25
Timestamp: 1704633218 Timestamp [UCT]: 2024-01-07 13:13:38 Age [y:d:h:m:s]: 01:069:12:46:07
Block: 930135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310814 RingCT/type: yes/0
Extra: 01679e2201f1f7ae71b56d4874e4b188001e1f8c7ca89ddcc316653c07a1583e2502110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09cf01860d3bc50c93c9fa193d133f6765d4998d79b846b5a59795dda8ce3419 0.600000000000 1388013 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": 930145, "vin": [ { "gen": { "height": 930135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09cf01860d3bc50c93c9fa193d133f6765d4998d79b846b5a59795dda8ce3419" } } ], "extra": [ 1, 103, 158, 34, 1, 241, 247, 174, 113, 181, 109, 72, 116, 228, 177, 136, 0, 30, 31, 140, 124, 168, 157, 220, 195, 22, 101, 60, 7, 161, 88, 62, 37, 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