Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1420d5c07eaf216045489c39215159d2a9104d1cf218f7bb3559cffe37719c1

Tx prefix hash: 4e24fcf9b1756c4738b15fbff0915f858f0f0305aebd3e4f8219d560585351c1
Tx public key: 032f9eec24e41f33417e6abf5e65e9846de7b51a128b88b13c9f6443da55f8d7
Timestamp: 1762902189 Timestamp [UCT]: 2025-11-11 23:03:09 Age [y:d:h:m:s]: 00:053:07:43:48
Block: 1410107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38197 RingCT/type: yes/0
Extra: 01032f9eec24e41f33417e6abf5e65e9846de7b51a128b88b13c9f6443da55f8d7021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66421ac113ce70b51b4ab8109c1a39a1438ec3f0bc029ec6bf03ff00e0abdde1 0.600000000000 1898556 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": 1410117, "vin": [ { "gen": { "height": 1410107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66421ac113ce70b51b4ab8109c1a39a1438ec3f0bc029ec6bf03ff00e0abdde1" } } ], "extra": [ 1, 3, 47, 158, 236, 36, 228, 31, 51, 65, 126, 106, 191, 94, 101, 233, 132, 109, 231, 181, 26, 18, 139, 136, 177, 60, 159, 100, 67, 218, 85, 248, 215, 2, 17, 0, 0, 0, 4, 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