Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 050f15579d7215df21ebfa5b6ef002386336070b9be8a70e71f4c5fc4886e0ed

Tx prefix hash: 990e19d6c1336f88563ddc72f99c5e035e32ef242e465516ea7c36d8b6d1ffae
Tx public key: 2fd39165b974e914199e7271b0702143ca50965f07762431d4695915c7e7c8c7
Timestamp: 1745476890 Timestamp [UCT]: 2025-04-24 06:41:30 Age [y:d:h:m:s]: 00:209:20:41:18
Block: 1268257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147712 RingCT/type: yes/0
Extra: 012fd39165b974e914199e7271b0702143ca50965f07762431d4695915c7e7c8c7021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dfd6d27998c5635d26f74a7a2b24b5a21740e78587c993d0c32d8d11c3c836d 0.600000000000 1755486 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": 1268267, "vin": [ { "gen": { "height": 1268257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dfd6d27998c5635d26f74a7a2b24b5a21740e78587c993d0c32d8d11c3c836d" } } ], "extra": [ 1, 47, 211, 145, 101, 185, 116, 233, 20, 25, 158, 114, 113, 176, 112, 33, 67, 202, 80, 150, 95, 7, 118, 36, 49, 212, 105, 89, 21, 199, 231, 200, 199, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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