Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b34592b3c461a62730abfbd41b5289afe68aa62f5b6aa11c68ef9da838c2b581

Tx prefix hash: f2b639a371baeb760f280f4804a09c66c651f57d463563c0c4d2705a4a430505
Tx public key: 0dc0e0b74fe7f8adc0157b91a25184655c17a188c25ce81564cb22f2cf485943
Timestamp: 1574559698 Timestamp [UCT]: 2019-11-24 01:41:38 Age [y:d:h:m:s]: 05:167:20:09:59
Block: 16074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1262638 RingCT/type: yes/0
Extra: 010dc0e0b74fe7f8adc0157b91a25184655c17a188c25ce81564cb22f2cf48594302110000000f354bbe3b000000000000000000

1 output(s) for total of 542.926510069000 dcy

stealth address amount amount idx
00: ba60c0ed34e03488c38c4d6f923a77f2959b168a17cc6e8041145466f1dcd03d 542.926510069000 22206 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": 16084, "vin": [ { "gen": { "height": 16074 } } ], "vout": [ { "amount": 542926510069, "target": { "key": "ba60c0ed34e03488c38c4d6f923a77f2959b168a17cc6e8041145466f1dcd03d" } } ], "extra": [ 1, 13, 192, 224, 183, 79, 231, 248, 173, 192, 21, 123, 145, 162, 81, 132, 101, 92, 23, 161, 136, 194, 92, 232, 21, 100, 203, 34, 242, 207, 72, 89, 67, 2, 17, 0, 0, 0, 15, 53, 75, 190, 59, 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