Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a68ab4c71eb316b955d16c02e30bd180034c79d9de11e4bdb0e021e4ff71a46

Tx prefix hash: e57ee284c92095ba23bd7059a90c9b10edfa90c077f28f2d1235ca39f8f529f9
Tx public key: 831df9e92e1c7a129d3fcee00fdbb46ab250b0f9f52405e8872073957ff608ba
Timestamp: 1728474862 Timestamp [UCT]: 2024-10-09 11:54:22 Age [y:d:h:m:s]: 00:169:13:27:32
Block: 1127812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120969 RingCT/type: yes/0
Extra: 01831df9e92e1c7a129d3fcee00fdbb46ab250b0f9f52405e8872073957ff608ba02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2cacc8cf7d07c7cbd5afa100c8d1b5633ad108eececf5ad87e84334e238bcb5 0.600000000000 1610625 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": 1127822, "vin": [ { "gen": { "height": 1127812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2cacc8cf7d07c7cbd5afa100c8d1b5633ad108eececf5ad87e84334e238bcb5" } } ], "extra": [ 1, 131, 29, 249, 233, 46, 28, 122, 18, 157, 63, 206, 224, 15, 219, 180, 106, 178, 80, 176, 249, 245, 36, 5, 232, 135, 32, 115, 149, 127, 246, 8, 186, 2, 17, 0, 0, 0, 1, 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