Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1cae464a0446102259c5ddb1a2c736967fa689d5d5b7095db636cbbe4e8b780

Tx prefix hash: d0ee7d845cda2edb63ff119d1a21fff864a6bdb65f005a6307e72f56cf889cbf
Tx public key: 722c947fe243ddc6f5ceb06b9ee0f93810552aaa6524ff74bd1d3a6050a27ef9
Timestamp: 1730536445 Timestamp [UCT]: 2024-11-02 08:34:05 Age [y:d:h:m:s]: 00:142:17:25:18
Block: 1144816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101834 RingCT/type: yes/0
Extra: 01722c947fe243ddc6f5ceb06b9ee0f93810552aaa6524ff74bd1d3a6050a27ef90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d73d4c761d8cb914b1e29c78cc77de3c814adeeca0a7f699fc7189bcd10bd059 0.600000000000 1629139 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": 1144826, "vin": [ { "gen": { "height": 1144816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d73d4c761d8cb914b1e29c78cc77de3c814adeeca0a7f699fc7189bcd10bd059" } } ], "extra": [ 1, 114, 44, 148, 127, 226, 67, 221, 198, 245, 206, 176, 107, 158, 224, 249, 56, 16, 85, 42, 170, 101, 36, 255, 116, 189, 29, 58, 96, 80, 162, 126, 249, 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