Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13d16d9f786240b79cfe92f73c3fe7c23ed58cfd3907216f71b812dd0b92263e

Tx prefix hash: ba69cad70c5e6d17364b0cab1d5f9916d993038ad785106f5dcaefa93b306bd0
Tx public key: 03e7490a029873d000f8e8764749aa64c6de17b3ef4fd0ba5be47ec57d34d23a
Timestamp: 1708265934 Timestamp [UCT]: 2024-02-18 14:18:54 Age [y:d:h:m:s]: 01:074:15:39:34
Block: 960271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314411 RingCT/type: yes/0
Extra: 0103e7490a029873d000f8e8764749aa64c6de17b3ef4fd0ba5be47ec57d34d23a0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 868ea9fc179801d06b45837a3ff2d71ea45f1a410491d4d44b3aeb0fa3529dc4 0.600000000000 1419834 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": 960281, "vin": [ { "gen": { "height": 960271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "868ea9fc179801d06b45837a3ff2d71ea45f1a410491d4d44b3aeb0fa3529dc4" } } ], "extra": [ 1, 3, 231, 73, 10, 2, 152, 115, 208, 0, 248, 232, 118, 71, 73, 170, 100, 198, 222, 23, 179, 239, 79, 208, 186, 91, 228, 126, 197, 125, 52, 210, 58, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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