Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d92f063822792ea6d6ed6d4616d7d15a82b0a40d3f504028d145ede05ac41ce

Tx prefix hash: fa676129e1cb0992fa4266ad237cb1fad06ae503836a3db1c458afa57b775f2f
Tx public key: 3ad2a8712eb9d422d56a8abf55db3e3dc9f703efe8234778526cd07bf92e055c
Timestamp: 1724084672 Timestamp [UCT]: 2024-08-19 16:24:32 Age [y:d:h:m:s]: 00:291:18:37:05
Block: 1091418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208453 RingCT/type: yes/0
Extra: 013ad2a8712eb9d422d56a8abf55db3e3dc9f703efe8234778526cd07bf92e055c02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07291f1471bdb0d2a097e34566c48e06cfb10d6f200fef10472531e83dd1b5b7 0.600000000000 1566049 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": 1091428, "vin": [ { "gen": { "height": 1091418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07291f1471bdb0d2a097e34566c48e06cfb10d6f200fef10472531e83dd1b5b7" } } ], "extra": [ 1, 58, 210, 168, 113, 46, 185, 212, 34, 213, 106, 138, 191, 85, 219, 62, 61, 201, 247, 3, 239, 232, 35, 71, 120, 82, 108, 208, 123, 249, 46, 5, 92, 2, 17, 0, 0, 0, 2, 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