Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e13d2dccccb46fcbe32545c2f5fc51bd80bba5d7bc81282d33784b7a42e1d181

Tx prefix hash: af607245ebe52695c1d4cc8ce3503e1fafe64f4e1cc3e372f84ba97d702d2a46
Tx public key: 3b11e45aa0f74393b1ff80412a3a9d09cf13c9a5cf6acf1f73e0c5c8f1f4b3fc
Timestamp: 1744995017 Timestamp [UCT]: 2025-04-18 16:50:17 Age [y:d:h:m:s]: 00:026:00:55:33
Block: 1264267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18640 RingCT/type: yes/0
Extra: 013b11e45aa0f74393b1ff80412a3a9d09cf13c9a5cf6acf1f73e0c5c8f1f4b3fc0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 697ebeed1cc955659423a24e38e95d1520df7bdf7e34a83259c24776ad49ccb6 0.600000000000 1751462 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": 1264277, "vin": [ { "gen": { "height": 1264267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "697ebeed1cc955659423a24e38e95d1520df7bdf7e34a83259c24776ad49ccb6" } } ], "extra": [ 1, 59, 17, 228, 90, 160, 247, 67, 147, 177, 255, 128, 65, 42, 58, 157, 9, 207, 19, 201, 165, 207, 106, 207, 31, 115, 224, 197, 200, 241, 244, 179, 252, 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