Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f14a8a45f7bfddaa29aae19b176a8575eafdb08337e8e26789fcdf5ba886b1f8

Tx prefix hash: 83db8af34209a3f7aa1407c0530bc95dd47fe7175e907e0f26a14b5573dcb87f
Tx public key: dd12e47c3e05bcc0f37af2e5b687ba359fa5e18b0156211a4081406b620ce75f
Timestamp: 1720711661 Timestamp [UCT]: 2024-07-11 15:27:41 Age [y:d:h:m:s]: 00:265:21:33:24
Block: 1063458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189963 RingCT/type: yes/0
Extra: 01dd12e47c3e05bcc0f37af2e5b687ba359fa5e18b0156211a4081406b620ce75f02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baa17b699adbb64b79e8d110916e08ac2c197fd25d913a240b617df09a376c0c 0.600000000000 1533973 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": 1063468, "vin": [ { "gen": { "height": 1063458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baa17b699adbb64b79e8d110916e08ac2c197fd25d913a240b617df09a376c0c" } } ], "extra": [ 1, 221, 18, 228, 124, 62, 5, 188, 192, 243, 122, 242, 229, 182, 135, 186, 53, 159, 165, 225, 139, 1, 86, 33, 26, 64, 129, 64, 107, 98, 12, 231, 95, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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