Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 984ff02b8db747c677a25ad7a901666bb4cf150ee9dfa4fcc94278ddc9e0677e

Tx prefix hash: 5f2e119bf0c4e342670b7bc590b415a1db330044e9745f38f6be4795161e2527
Tx public key: 85793a2c4b09c0a5ae904f6f10b503d660a6a6aa66c913c18cc840a2c9f52436
Timestamp: 1737066460 Timestamp [UCT]: 2025-01-16 22:27:40 Age [y:d:h:m:s]: 00:059:14:01:11
Block: 1198896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42373 RingCT/type: yes/0
Extra: 0185793a2c4b09c0a5ae904f6f10b503d660a6a6aa66c913c18cc840a2c9f52436021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b4f728ea767e180ee6954d0ee7a5e0f4102f3cd4381e1ea0d5c4ff6f2d33a15 0.600000000000 1685523 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": 1198906, "vin": [ { "gen": { "height": 1198896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b4f728ea767e180ee6954d0ee7a5e0f4102f3cd4381e1ea0d5c4ff6f2d33a15" } } ], "extra": [ 1, 133, 121, 58, 44, 75, 9, 192, 165, 174, 144, 79, 111, 16, 181, 3, 214, 96, 166, 166, 170, 102, 201, 19, 193, 140, 200, 64, 162, 201, 245, 36, 54, 2, 17, 0, 0, 0, 7, 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