Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dbfd641ad18b3ca68bbcd3d08c8dd63bfb15dd44cc203fef3c3b3120d8dbaf8

Tx prefix hash: 104e79eb059f9f9f1c16f342e60857a6081101e5fbb8cb0735c4f15375894b03
Tx public key: ee2d4aaf6b40c1d6079164b7052f031a3488dee8062df3da609881a159007f58
Timestamp: 1751355744 Timestamp [UCT]: 2025-07-01 07:42:24 Age [y:d:h:m:s]: 00:142:17:57:13
Block: 1316400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100218 RingCT/type: yes/0
Extra: 01ee2d4aaf6b40c1d6079164b7052f031a3488dee8062df3da609881a159007f5802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fddd95703025a09c1c214d2c40f0c01911acb6b1377f833ab6c81f48d67fe937 0.600000000000 1804059 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": 1316410, "vin": [ { "gen": { "height": 1316400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fddd95703025a09c1c214d2c40f0c01911acb6b1377f833ab6c81f48d67fe937" } } ], "extra": [ 1, 238, 45, 74, 175, 107, 64, 193, 214, 7, 145, 100, 183, 5, 47, 3, 26, 52, 136, 222, 232, 6, 45, 243, 218, 96, 152, 129, 161, 89, 0, 127, 88, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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