Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f3992bafcbe335bafca1d5ddcc66b752a0be861a91a9c60428bdad3c6a057e9

Tx prefix hash: 937f74cf2f3c4de3912a0cf53b589673e5a086f2c72dc11521c0248c8cf71072
Tx public key: 5160fa4f969eee8b5d945e7eb3ddeca7c8375122d1ab67d2d97884014a28a48a
Timestamp: 1762186020 Timestamp [UCT]: 2025-11-03 16:07:00 Age [y:d:h:m:s]: 00:017:09:38:24
Block: 1404166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12455 RingCT/type: yes/0
Extra: 015160fa4f969eee8b5d945e7eb3ddeca7c8375122d1ab67d2d97884014a28a48a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4059bf71e546d58d4765c870a75e644de0ef59f7de299dc49bef37f426e9e285 0.600000000000 1892523 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": 1404176, "vin": [ { "gen": { "height": 1404166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4059bf71e546d58d4765c870a75e644de0ef59f7de299dc49bef37f426e9e285" } } ], "extra": [ 1, 81, 96, 250, 79, 150, 158, 238, 139, 93, 148, 94, 126, 179, 221, 236, 167, 200, 55, 81, 34, 209, 171, 103, 210, 217, 120, 132, 1, 74, 40, 164, 138, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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