Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0a281393b0fa23ebae3438f6519b05d8ffcb22c893655d8234adf356f1dbe73

Tx prefix hash: d4d8af07616a2bda9bab6f8e2c162c2a567211bba34e38295787556aebbb9e52
Tx public key: 24b7aa7d8dd0bc73e21215538ccbcc4080af4c7ab1d81f6db8146e667b0dd682
Timestamp: 1702278095 Timestamp [UCT]: 2023-12-11 07:01:35 Age [y:d:h:m:s]: 00:352:22:42:58
Block: 910623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252723 RingCT/type: yes/0
Extra: 0124b7aa7d8dd0bc73e21215538ccbcc4080af4c7ab1d81f6db8146e667b0dd682021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f51732a1465c7ed956ca659de338b69191165912c814aebea6d7f891bb164d4 0.600000000000 1367784 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": 910633, "vin": [ { "gen": { "height": 910623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f51732a1465c7ed956ca659de338b69191165912c814aebea6d7f891bb164d4" } } ], "extra": [ 1, 36, 183, 170, 125, 141, 208, 188, 115, 226, 18, 21, 83, 140, 203, 204, 64, 128, 175, 76, 122, 177, 216, 31, 109, 184, 20, 110, 102, 123, 13, 214, 130, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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