Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 446db6208b30186f15c153e0781d3a01e037ed713f03a7398b517aa41601fff0

Tx prefix hash: dcd06be9cd387f499c738fb1935ecbfd710f2c11f369d89b262f7d358d25152d
Tx public key: f0068dac44ff033d5bcee1dc6c4d8b9179e04a71bf1510f81c49a595f05ba461
Timestamp: 1766084098 Timestamp [UCT]: 2025-12-18 18:54:58 Age [y:d:h:m:s]: 00:002:15:16:00
Block: 1436479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1882 RingCT/type: yes/0
Extra: 01f0068dac44ff033d5bcee1dc6c4d8b9179e04a71bf1510f81c49a595f05ba46102110000000ed6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afd200f901a3e4f40968ecc37febaba5ebeec0e26c1530eaa0fbf05d63dc3513 0.600000000000 1925284 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": 1436489, "vin": [ { "gen": { "height": 1436479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afd200f901a3e4f40968ecc37febaba5ebeec0e26c1530eaa0fbf05d63dc3513" } } ], "extra": [ 1, 240, 6, 141, 172, 68, 255, 3, 61, 91, 206, 225, 220, 108, 77, 139, 145, 121, 224, 74, 113, 191, 21, 16, 248, 28, 73, 165, 149, 240, 91, 164, 97, 2, 17, 0, 0, 0, 14, 214, 225, 157, 124, 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