Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de47b5146650bf09848883a22828ffac3d18723f483069a83fddc1e01d48b39f

Tx prefix hash: ae0b63cf832edfdee123ddecb22996d009043340272af5dae0c5c7b418934b60
Tx public key: bdc75b3ddc3c18efd9ee407b446f2a9b332396cc5b5c7dff123174708cf9d0c0
Timestamp: 1726436143 Timestamp [UCT]: 2024-09-15 21:35:43 Age [y:d:h:m:s]: 00:128:19:28:14
Block: 1110915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92068 RingCT/type: yes/0
Extra: 01bdc75b3ddc3c18efd9ee407b446f2a9b332396cc5b5c7dff123174708cf9d0c0021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f777c402cd64e71f802d93e8464e46efe39836d879778a63e00034d993ab806e 0.600000000000 1589692 of 15

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": 1110925, "vin": [ { "gen": { "height": 1110915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f777c402cd64e71f802d93e8464e46efe39836d879778a63e00034d993ab806e" } } ], "extra": [ 1, 189, 199, 91, 61, 220, 60, 24, 239, 217, 238, 64, 123, 68, 111, 42, 155, 51, 35, 150, 204, 91, 92, 125, 255, 18, 49, 116, 112, 140, 249, 208, 192, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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