Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b743102cf6a4775d2f8d9d13102a1591329e3486e817f95f3c20764adf64063

Tx prefix hash: a6958683250f8e1e2114b62a90779ccc649c8d8de47cc817b7c3fd5fb79cdc6f
Tx public key: bea6bb296e1a74140c1deed72b3f7987d84791f441d116d467e6df2c48a00e09
Timestamp: 1730674356 Timestamp [UCT]: 2024-11-03 22:52:36 Age [y:d:h:m:s]: 00:077:14:09:13
Block: 1145963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55467 RingCT/type: yes/0
Extra: 01bea6bb296e1a74140c1deed72b3f7987d84791f441d116d467e6df2c48a00e090211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59a4be7bde5ede766c3b7826a24cf3175b7fef648ffa00a4619f5c17025e4b76 0.600000000000 1630502 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": 1145973, "vin": [ { "gen": { "height": 1145963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59a4be7bde5ede766c3b7826a24cf3175b7fef648ffa00a4619f5c17025e4b76" } } ], "extra": [ 1, 190, 166, 187, 41, 110, 26, 116, 20, 12, 29, 238, 215, 43, 63, 121, 135, 216, 71, 145, 244, 65, 209, 22, 212, 103, 230, 223, 44, 72, 160, 14, 9, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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