Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cb3d29537ca0e97db9f67b5ee85816af4ef61816f63d5f1dd2c1fc60b36cfe4

Tx prefix hash: ff07097284ff414924a3e05c4cd11b7d3c033fac69c591c966f0c720ff6d8d77
Tx public key: cc149282bc5b9ab9e9d7c16672969d19610f117007b0dc013f4815faaad72e0f
Timestamp: 1710542172 Timestamp [UCT]: 2024-03-15 22:36:12 Age [y:d:h:m:s]: 01:099:09:49:27
Block: 979164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331864 RingCT/type: yes/0
Extra: 01cc149282bc5b9ab9e9d7c16672969d19610f117007b0dc013f4815faaad72e0f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e50d22f08a5c8cac759be8f924398f3e57adaab049449e4543aac6d9731fefc 0.600000000000 1439197 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": 979174, "vin": [ { "gen": { "height": 979164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e50d22f08a5c8cac759be8f924398f3e57adaab049449e4543aac6d9731fefc" } } ], "extra": [ 1, 204, 20, 146, 130, 188, 91, 154, 185, 233, 215, 193, 102, 114, 150, 157, 25, 97, 15, 17, 112, 7, 176, 220, 1, 63, 72, 21, 250, 170, 215, 46, 15, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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