Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d500fd0e9e5134f672e2d93c6a40c7858f1ebe73762af67a0305022b19d7041f

Tx prefix hash: 783a3e80c278bf6aef727cd4a1783ee02a1a030761016f07ab425046e3c67cd4
Tx public key: a2174bd2e628928a9ab6aee9399104c09d223f4035dc18a1990f2ad439429a82
Timestamp: 1574496657 Timestamp [UCT]: 2019-11-23 08:10:57 Age [y:d:h:m:s]: 05:172:16:16:07
Block: 15273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1266384 RingCT/type: yes/0
Extra: 01a2174bd2e628928a9ab6aee9399104c09d223f4035dc18a1990f2ad439429a82021100000008f95225a5000000000000000000

1 output(s) for total of 546.272724217000 dcy

stealth address amount amount idx
00: 158feffab5a9fc1ed574924ce98a3c2e5541d5158aa8c5c2368658988cc882a4 546.272724217000 20310 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": 15283, "vin": [ { "gen": { "height": 15273 } } ], "vout": [ { "amount": 546272724217, "target": { "key": "158feffab5a9fc1ed574924ce98a3c2e5541d5158aa8c5c2368658988cc882a4" } } ], "extra": [ 1, 162, 23, 75, 210, 230, 40, 146, 138, 154, 182, 174, 233, 57, 145, 4, 192, 157, 34, 63, 64, 53, 220, 24, 161, 153, 15, 42, 212, 57, 66, 154, 130, 2, 17, 0, 0, 0, 8, 249, 82, 37, 165, 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