Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d677536dbc4c11c2cb9dda9b6e4d02f0aabbd0318badf70412221cf72bb7acb9

Tx prefix hash: bfe0e097182257090ffd8b2f5326a391dc004faf6e5c59061fe10abacc06a70f
Tx public key: be181223c65795b21a316008aa3e2844c38e0f2ca29d7d681e9a954977a0d4a0
Timestamp: 1705517365 Timestamp [UCT]: 2024-01-17 18:49:25 Age [y:d:h:m:s]: 01:078:20:16:14
Block: 937460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317454 RingCT/type: yes/0
Extra: 01be181223c65795b21a316008aa3e2844c38e0f2ca29d7d681e9a954977a0d4a00211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68227c9e1e0c70208ad45a96232b278c8a3470b1ef89fd97a52dc49a968138b7 0.600000000000 1395514 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": 937470, "vin": [ { "gen": { "height": 937460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68227c9e1e0c70208ad45a96232b278c8a3470b1ef89fd97a52dc49a968138b7" } } ], "extra": [ 1, 190, 24, 18, 35, 198, 87, 149, 178, 26, 49, 96, 8, 170, 62, 40, 68, 195, 142, 15, 44, 162, 157, 125, 104, 30, 154, 149, 73, 119, 160, 212, 160, 2, 17, 0, 0, 0, 3, 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