Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f761948a063499a32b5072bbd6955e45d81e5303eba85c4dfb69df9f4ef04491

Tx prefix hash: 33e88ed180f68d1e4f1ecd96c55cabb2d96fad0a0da94ef07bb9fc95c14516db
Tx public key: dea5fbaa01931e9e4eafdd1db055bba1e6283a224a0af9285a69df250eb82d7a
Timestamp: 1737903010 Timestamp [UCT]: 2025-01-26 14:50:10 Age [y:d:h:m:s]: 00:143:23:33:05
Block: 1205776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102645 RingCT/type: yes/0
Extra: 01dea5fbaa01931e9e4eafdd1db055bba1e6283a224a0af9285a69df250eb82d7a02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01052112a27a4d4351c810248a0215ca260bb105fc61ce1fa0c5cb11aa6fedf9 0.600000000000 1692475 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": 1205786, "vin": [ { "gen": { "height": 1205776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01052112a27a4d4351c810248a0215ca260bb105fc61ce1fa0c5cb11aa6fedf9" } } ], "extra": [ 1, 222, 165, 251, 170, 1, 147, 30, 158, 78, 175, 221, 29, 176, 85, 187, 161, 230, 40, 58, 34, 74, 10, 249, 40, 90, 105, 223, 37, 14, 184, 45, 122, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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