Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f7aa818de426d370fb09434ac303bb086ab11719dcad9e4dfeb0828d2274eee

Tx prefix hash: ba4f29eb1656fbe751265d558c7bc18a90a62dbc64f4693acc21dc7a4f221bd0
Tx public key: 7fa19f1d5d0855c278f8557566df41e5b33825d21dd6fa3427aaecaab598b0a4
Timestamp: 1736540225 Timestamp [UCT]: 2025-01-10 20:17:05 Age [y:d:h:m:s]: 00:070:12:20:30
Block: 1194543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50170 RingCT/type: yes/0
Extra: 017fa19f1d5d0855c278f8557566df41e5b33825d21dd6fa3427aaecaab598b0a402110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bd6e82c693669ae97e872d9b9798ca8f73c4a47f1cce6c3ea6e78ede89ca2f5 0.600000000000 1681118 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": 1194553, "vin": [ { "gen": { "height": 1194543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bd6e82c693669ae97e872d9b9798ca8f73c4a47f1cce6c3ea6e78ede89ca2f5" } } ], "extra": [ 1, 127, 161, 159, 29, 93, 8, 85, 194, 120, 248, 85, 117, 102, 223, 65, 229, 179, 56, 37, 210, 29, 214, 250, 52, 39, 170, 236, 170, 181, 152, 176, 164, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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