Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63748c45eaa919f708a6f6652252ed6cc345ad2844105f6f4290bec7c7e02ae1

Tx prefix hash: 06388c18fea1a2ef0115d0fe520eb497acbbbc8c2ec1c1435f913e3d91167415
Tx public key: 9adfd030f4bd5f478f84c2f069074bbdf66ab975e595d1088828c4d105b6f890
Timestamp: 1684884244 Timestamp [UCT]: 2023-05-23 23:24:04 Age [y:d:h:m:s]: 02:170:02:57:11
Block: 766676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 641384 RingCT/type: yes/0
Extra: 019adfd030f4bd5f478f84c2f069074bbdf66ab975e595d1088828c4d105b6f890021100000003faf35c9c000000000000000000

1 output(s) for total of 1.768822803000 dcy

stealth address amount amount idx
00: 8074363cd4fe99324fcb643310682c027a8acfd34fd611fed9fb7cd0ca93e2c3 1.768822803000 1215733 of 0

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": 766686, "vin": [ { "gen": { "height": 766676 } } ], "vout": [ { "amount": 1768822803, "target": { "key": "8074363cd4fe99324fcb643310682c027a8acfd34fd611fed9fb7cd0ca93e2c3" } } ], "extra": [ 1, 154, 223, 208, 48, 244, 189, 95, 71, 143, 132, 194, 240, 105, 7, 75, 189, 246, 106, 185, 117, 229, 149, 209, 8, 136, 40, 196, 209, 5, 182, 248, 144, 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