Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5161e2e6cc56d13fdbaf6e553318d522c6df07a7d9e94255e202c9a6100271cb

Tx prefix hash: f37b623e4325138982a76322bbb61b54b996ca7c4e7cb07a4eb3db2e75d21fad
Tx public key: 4124842d18e31c9e41e83858f3cfa43b83067f1d18cc517d7c43f7e9ff5aa9d1
Timestamp: 1714257412 Timestamp [UCT]: 2024-04-27 22:36:52 Age [y:d:h:m:s]: 00:249:17:23:45
Block: 1009941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178751 RingCT/type: yes/0
Extra: 014124842d18e31c9e41e83858f3cfa43b83067f1d18cc517d7c43f7e9ff5aa9d10211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1641259dd8e00975156c755c11c19ca2ea207fa6794d6ba038ad6a6e1c5533f9 0.600000000000 1471755 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": 1009951, "vin": [ { "gen": { "height": 1009941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1641259dd8e00975156c755c11c19ca2ea207fa6794d6ba038ad6a6e1c5533f9" } } ], "extra": [ 1, 65, 36, 132, 45, 24, 227, 28, 158, 65, 232, 56, 88, 243, 207, 164, 59, 131, 6, 127, 29, 24, 204, 81, 125, 124, 67, 247, 233, 255, 90, 169, 209, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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