Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 730a29095c599a5fa7f91bb76a64bd1acfbce9cd2628f9ebf020ce0338408532

Tx prefix hash: 4553eaa61199a7a90f826844c23ad0d6c4719a4a4a6ffe307268c4a7f2cad2fd
Tx public key: 99e2638858d30f1635b8e72878d5310c7541e4465abdabea265d65a9f381b9f9
Timestamp: 1699835697 Timestamp [UCT]: 2023-11-13 00:34:57 Age [y:d:h:m:s]: 01:164:00:51:25
Block: 890398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378421 RingCT/type: yes/0
Extra: 0199e2638858d30f1635b8e72878d5310c7541e4465abdabea265d65a9f381b9f90211000000076afc55ed000000000000000000

1 output(s) for total of 0.688242998000 dcy

stealth address amount amount idx
00: 310d5ae5facd378cd5557e5a6118b7ed5f4d67699f96a5246d2831372c895b37 0.688242998000 1346421 of 0

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": 890408, "vin": [ { "gen": { "height": 890398 } } ], "vout": [ { "amount": 688242998, "target": { "key": "310d5ae5facd378cd5557e5a6118b7ed5f4d67699f96a5246d2831372c895b37" } } ], "extra": [ 1, 153, 226, 99, 136, 88, 211, 15, 22, 53, 184, 231, 40, 120, 213, 49, 12, 117, 65, 228, 70, 90, 189, 171, 234, 38, 93, 101, 169, 243, 129, 185, 249, 2, 17, 0, 0, 0, 7, 106, 252, 85, 237, 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