Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d85d3f4fc7a1d5121d08f914455b28d1ad866a616e8fd12cdd48675b12493bc

Tx prefix hash: 2bea5648ca4062b1a588859b80b11e8ac7588cbc5d7bf2ae12b0ff24a976d137
Tx public key: c89f2313c71dbb560a8ce59626a6c4cfeeb72032ba6e118b221c88a8cfe71a85
Timestamp: 1733033185 Timestamp [UCT]: 2024-12-01 06:06:25 Age [y:d:h:m:s]: 00:027:05:06:17
Block: 1165514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19458 RingCT/type: yes/0
Extra: 01c89f2313c71dbb560a8ce59626a6c4cfeeb72032ba6e118b221c88a8cfe71a8502110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df7561570b08192550390a6df0bc9e41f712963b5c930092224c666f63974e2c 0.600000000000 1651189 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": 1165524, "vin": [ { "gen": { "height": 1165514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df7561570b08192550390a6df0bc9e41f712963b5c930092224c666f63974e2c" } } ], "extra": [ 1, 200, 159, 35, 19, 199, 29, 187, 86, 10, 140, 229, 150, 38, 166, 196, 207, 238, 183, 32, 50, 186, 110, 17, 139, 34, 28, 136, 168, 207, 231, 26, 133, 2, 17, 0, 0, 0, 11, 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