Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 679e8b75917b0bcd25183552b49f10848e2341b3ac011ba521204575c654aeb2

Tx prefix hash: 939735e52bb910ff8e10fb18bde515e6f2667b7b172677c6b99efaa5a134a2cf
Tx public key: d6e82c08a837e9675c4acd6d29ae0765fb7cbd183c33a10e75934af55d5c7b84
Timestamp: 1577654728 Timestamp [UCT]: 2019-12-29 21:25:28 Age [y:d:h:m:s]: 05:076:14:58:24
Block: 34562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1204566 RingCT/type: yes/0
Extra: 01d6e82c08a837e9675c4acd6d29ae0765fb7cbd183c33a10e75934af55d5c7b840211000000018a2ee0d9000000000000000000

1 output(s) for total of 471.500982704000 dcy

stealth address amount amount idx
00: 2732ff563fea5227f208bf5876b041c2706e032c55d1333ea53bf9382842feec 471.500982704000 58192 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": 34572, "vin": [ { "gen": { "height": 34562 } } ], "vout": [ { "amount": 471500982704, "target": { "key": "2732ff563fea5227f208bf5876b041c2706e032c55d1333ea53bf9382842feec" } } ], "extra": [ 1, 214, 232, 44, 8, 168, 55, 233, 103, 92, 74, 205, 109, 41, 174, 7, 101, 251, 124, 189, 24, 60, 51, 161, 14, 117, 147, 74, 245, 93, 92, 123, 132, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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