Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1b789d04e357915c8af85a76723ccd09fb3562a0a427a0cf6549df659c0f2d

Tx prefix hash: 17de809d20b48bae9f316b4ab227f9db84a0a092c76cfb6fb038ee845a9b5298
Tx public key: 3d23c9fa34dca52a58837d4789583bb5f95b1a2572a10f805894ee2fcd720b14
Timestamp: 1712034747 Timestamp [UCT]: 2024-04-02 05:12:27 Age [y:d:h:m:s]: 01:074:13:12:22
Block: 991489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314219 RingCT/type: yes/0
Extra: 013d23c9fa34dca52a58837d4789583bb5f95b1a2572a10f805894ee2fcd720b1402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34d1cfd43cd3891787ec91ae2fa13b1656992249ad412a3505fed067e0037ea1 0.600000000000 1451825 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": 991499, "vin": [ { "gen": { "height": 991489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34d1cfd43cd3891787ec91ae2fa13b1656992249ad412a3505fed067e0037ea1" } } ], "extra": [ 1, 61, 35, 201, 250, 52, 220, 165, 42, 88, 131, 125, 71, 137, 88, 59, 181, 249, 91, 26, 37, 114, 161, 15, 128, 88, 148, 238, 47, 205, 114, 11, 20, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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