Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 172919ce8f9e90bf4df60e923eab1ff9f2a86d79e86ff2951dd3ad516c923802

Tx prefix hash: 5775917c40b1363f0f420051dd5a542b9f5d1beed46bab56c804ddf618bff0cb
Tx public key: c83af8dabd46922461b4f89c42965056f14fce7cc1e7a3e8030cc86ebaa15bca
Timestamp: 1730347965 Timestamp [UCT]: 2024-10-31 04:12:45 Age [y:d:h:m:s]: 00:007:12:00:51
Block: 1143260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5375 RingCT/type: yes/0
Extra: 01c83af8dabd46922461b4f89c42965056f14fce7cc1e7a3e8030cc86ebaa15bca0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd7c9310dde44649253f5015b7cd4c1d49d6ed233a3c8e01ded9d8c99f75d403 0.600000000000 1627123 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": 1143270, "vin": [ { "gen": { "height": 1143260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd7c9310dde44649253f5015b7cd4c1d49d6ed233a3c8e01ded9d8c99f75d403" } } ], "extra": [ 1, 200, 58, 248, 218, 189, 70, 146, 36, 97, 180, 248, 156, 66, 150, 80, 86, 241, 79, 206, 124, 193, 231, 163, 232, 3, 12, 200, 110, 186, 161, 91, 202, 2, 17, 0, 0, 0, 2, 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