Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7af8676bab10c1cd45eb5af5dab6dc28e647c7f21fc906c843d0ab823f080eb

Tx prefix hash: b7d7c06cd101d8b94720330cbd77c06e0344bf23becde024e4e4a54731ec0e8f
Tx public key: a394db50b5701cd1c238eb0712076fa7632f478d8c1b6b610658de21e9e541b6
Timestamp: 1723433759 Timestamp [UCT]: 2024-08-12 03:35:59 Age [y:d:h:m:s]: 00:194:19:19:24
Block: 1086019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139075 RingCT/type: yes/0
Extra: 01a394db50b5701cd1c238eb0712076fa7632f478d8c1b6b610658de21e9e541b602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c73c958aaf4280370b2324b10df49d40aa8f6c29414ab23a213d41049d57db5a 0.600000000000 1560612 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": 1086029, "vin": [ { "gen": { "height": 1086019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c73c958aaf4280370b2324b10df49d40aa8f6c29414ab23a213d41049d57db5a" } } ], "extra": [ 1, 163, 148, 219, 80, 181, 112, 28, 209, 194, 56, 235, 7, 18, 7, 111, 167, 99, 47, 71, 141, 140, 27, 107, 97, 6, 88, 222, 33, 233, 229, 65, 182, 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