Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a9078a2cdc0acb3271cc02ce5639aaa0eba0756dc607a9115ed4ecb0ba68c95

Tx prefix hash: c1f8824b2afb10718116daf72b387e471c34461585ac6ad2037ef45164da0461
Tx public key: 633cb1ae77530506ad37a76d2c7132f4777f0c5d469fd5c7545a3f5a8598270d
Timestamp: 1717876938 Timestamp [UCT]: 2024-06-08 20:02:18 Age [y:d:h:m:s]: 00:290:10:26:41
Block: 1039950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207547 RingCT/type: yes/0
Extra: 01633cb1ae77530506ad37a76d2c7132f4777f0c5d469fd5c7545a3f5a8598270d021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770f4cb1eff13ae7a7b0dae45b10bfe729669e3bb9770193c6f928b3e26bef5e 0.600000000000 1508605 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": 1039960, "vin": [ { "gen": { "height": 1039950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770f4cb1eff13ae7a7b0dae45b10bfe729669e3bb9770193c6f928b3e26bef5e" } } ], "extra": [ 1, 99, 60, 177, 174, 119, 83, 5, 6, 173, 55, 167, 109, 44, 113, 50, 244, 119, 127, 12, 93, 70, 159, 213, 199, 84, 90, 63, 90, 133, 152, 39, 13, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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