Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bec9e2ae4f0e0cda5d8466cf204688d76e8eb0b01826829800e6bbb60358c03b

Tx prefix hash: 80b561e161dbc5dbcba5cc0b4d5750e9f1eb5f917f115f641d1e6dea7869d699
Tx public key: 48e5184464715d49630f973df3ee01b0830a65a9272e9f2dce18871a23d78a4f
Timestamp: 1702681499 Timestamp [UCT]: 2023-12-15 23:04:59 Age [y:d:h:m:s]: 01:135:02:14:14
Block: 913969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357712 RingCT/type: yes/0
Extra: 0148e5184464715d49630f973df3ee01b0830a65a9272e9f2dce18871a23d78a4f02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a37a2d129a00a54306a33791fd1a3a3004ad214131707f766326d01071cc7f1 0.600000000000 1371249 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": 913979, "vin": [ { "gen": { "height": 913969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a37a2d129a00a54306a33791fd1a3a3004ad214131707f766326d01071cc7f1" } } ], "extra": [ 1, 72, 229, 24, 68, 100, 113, 93, 73, 99, 15, 151, 61, 243, 238, 1, 176, 131, 10, 101, 169, 39, 46, 159, 45, 206, 24, 135, 26, 35, 215, 138, 79, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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