Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e23636f71567727824c4edb5119d8b3d5dcb8f02a2db22eced28b78550e41b4d

Tx prefix hash: 9ce069576f563acd9796812c1de79b17e44cd99760f3dca9b0fd2f54d9a8b84a
Tx public key: b3c5250f9f3aa56b6b0cbc4188d7e860558a8f1be1ff1bc45e8392da5d4165cd
Timestamp: 1650642099 Timestamp [UCT]: 2022-04-22 15:41:39 Age [y:d:h:m:s]: 02:331:19:50:03
Block: 485765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 756909 RingCT/type: yes/0
Extra: 01b3c5250f9f3aa56b6b0cbc4188d7e860558a8f1be1ff1bc45e8392da5d4165cd02110000000b75e3f0e9000000000000000000

1 output(s) for total of 15.082006747000 dcy

stealth address amount amount idx
00: 4bad4a31e884800c5520792e1f3884164c066e1d2456109de55182dc36678f9e 15.082006747000 907904 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": 485775, "vin": [ { "gen": { "height": 485765 } } ], "vout": [ { "amount": 15082006747, "target": { "key": "4bad4a31e884800c5520792e1f3884164c066e1d2456109de55182dc36678f9e" } } ], "extra": [ 1, 179, 197, 37, 15, 159, 58, 165, 107, 107, 12, 188, 65, 136, 215, 232, 96, 85, 138, 143, 27, 225, 255, 27, 196, 94, 131, 146, 218, 93, 65, 101, 205, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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