Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c9f1e8f769d1ea2c6f835d6d6de67f250951a21f32a1ca435e54358c9b46708

Tx prefix hash: db65a3edb859761ee138dfc3bd15886465c3acf8f0b6ecb06633addc4a8d67d1
Tx public key: 9360a3e9639fce1525536adbf818dc23655e438636d08e9b5d71bf58d120a4b3
Timestamp: 1651080618 Timestamp [UCT]: 2022-04-27 17:30:18 Age [y:d:h:m:s]: 02:322:11:20:22
Block: 489367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 750240 RingCT/type: yes/0
Extra: 019360a3e9639fce1525536adbf818dc23655e438636d08e9b5d71bf58d120a4b3021100000001c9067537000000000000000000

1 output(s) for total of 14.673178615000 dcy

stealth address amount amount idx
00: 5625618beb7efd70e64ed1f01c8e14a549480f992abc7a44f59c5165c956e5df 14.673178615000 912164 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": 489377, "vin": [ { "gen": { "height": 489367 } } ], "vout": [ { "amount": 14673178615, "target": { "key": "5625618beb7efd70e64ed1f01c8e14a549480f992abc7a44f59c5165c956e5df" } } ], "extra": [ 1, 147, 96, 163, 233, 99, 159, 206, 21, 37, 83, 106, 219, 248, 24, 220, 35, 101, 94, 67, 134, 54, 208, 142, 155, 93, 113, 191, 88, 209, 32, 164, 179, 2, 17, 0, 0, 0, 1, 201, 6, 117, 55, 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