Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b48b14d3d642ce99ce6977af80ea58a7a914416f4d6334c55f1c3d2faf270142

Tx prefix hash: e569b5dbf31b4707a644c7498740685c5f3b4bd74c4933d4605f067429a3c3b4
Tx public key: 344ddfe8f809b410be2cff6cdf5e166850d33958b90907d6bbfbfbaf8c6277d8
Timestamp: 1729502597 Timestamp [UCT]: 2024-10-21 09:23:17 Age [y:d:h:m:s]: 00:034:04:11:09
Block: 1136298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24417 RingCT/type: yes/0
Extra: 01344ddfe8f809b410be2cff6cdf5e166850d33958b90907d6bbfbfbaf8c6277d8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f66b05685d49d6271ea6c3130e38aef9cebe30ced26e1c12b532698746254ebc 0.600000000000 1619643 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": 1136308, "vin": [ { "gen": { "height": 1136298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f66b05685d49d6271ea6c3130e38aef9cebe30ced26e1c12b532698746254ebc" } } ], "extra": [ 1, 52, 77, 223, 232, 248, 9, 180, 16, 190, 44, 255, 108, 223, 94, 22, 104, 80, 211, 57, 88, 185, 9, 7, 214, 187, 251, 251, 175, 140, 98, 119, 216, 2, 17, 0, 0, 0, 1, 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