Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 917f2badc1dbd1ffeb01a9593df8cc6110f5e3b067ce3265cef231b6c1395525

Tx prefix hash: 128b7e4fc73d8f9f4d7b2317179963befa25d6a107837ab9733e0ad9fdb0cbcf
Tx public key: 049e5a47a4bb7b285dff3fa8c120360ddd05776b2f61a143ba471cfa96848cb8
Timestamp: 1745644528 Timestamp [UCT]: 2025-04-26 05:15:28 Age [y:d:h:m:s]: 00:216:01:08:20
Block: 1269644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152143 RingCT/type: yes/0
Extra: 01049e5a47a4bb7b285dff3fa8c120360ddd05776b2f61a143ba471cfa96848cb80211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18da7376c1217b9425d4a6d3ea616cb13d69b7a5a35ad01ff3b27d7b900569f5 0.600000000000 1756883 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": 1269654, "vin": [ { "gen": { "height": 1269644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18da7376c1217b9425d4a6d3ea616cb13d69b7a5a35ad01ff3b27d7b900569f5" } } ], "extra": [ 1, 4, 158, 90, 71, 164, 187, 123, 40, 93, 255, 63, 168, 193, 32, 54, 13, 221, 5, 119, 107, 47, 97, 161, 67, 186, 71, 28, 250, 150, 132, 140, 184, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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