Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c3ec37977364eb70a5f34f363f64bd48ffb11fbb00a1f1183c68b97bfffc6b2

Tx prefix hash: cd88b88287f916b4a3567a0a0291bd89e35c0a649f4b0f6986c19ba229f17e34
Tx public key: 02314124570706e8eeb1dddf2a3bbc243158cae010c7b0478a0c9e952492e551
Timestamp: 1730517862 Timestamp [UCT]: 2024-11-02 03:24:22 Age [y:d:h:m:s]: 00:137:09:52:47
Block: 1144669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98061 RingCT/type: yes/0
Extra: 0102314124570706e8eeb1dddf2a3bbc243158cae010c7b0478a0c9e952492e5510211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8ba3d68d7087281704298b776420843c7a9ba56a0c843c293495bbf5f9fead1 0.600000000000 1628944 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": 1144679, "vin": [ { "gen": { "height": 1144669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8ba3d68d7087281704298b776420843c7a9ba56a0c843c293495bbf5f9fead1" } } ], "extra": [ 1, 2, 49, 65, 36, 87, 7, 6, 232, 238, 177, 221, 223, 42, 59, 188, 36, 49, 88, 202, 224, 16, 199, 176, 71, 138, 12, 158, 149, 36, 146, 229, 81, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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