Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f76799944188b27c0d6168848de556ce60229dbb0a14a6f50b3a105fc6366595

Tx prefix hash: 19f5020826d605f98b3a69c1320156141fc626c38f1f74108d35b684ad112908
Tx public key: 0b852e02bc60c2d1a6294ff95404d02bf1408f2bd93ca5a17cab7e8e9c934df8
Timestamp: 1713059214 Timestamp [UCT]: 2024-04-14 01:46:54 Age [y:d:h:m:s]: 01:232:01:18:52
Block: 999997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424556 RingCT/type: yes/0
Extra: 010b852e02bc60c2d1a6294ff95404d02bf1408f2bd93ca5a17cab7e8e9c934df80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8c9ff7f279928110fcc3b96daaa8d7d0f7e5f118324bbc95d6a5caa247efd33 0.600000000000 1460485 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": 1000007, "vin": [ { "gen": { "height": 999997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8c9ff7f279928110fcc3b96daaa8d7d0f7e5f118324bbc95d6a5caa247efd33" } } ], "extra": [ 1, 11, 133, 46, 2, 188, 96, 194, 209, 166, 41, 79, 249, 84, 4, 208, 43, 241, 64, 143, 43, 217, 60, 165, 161, 124, 171, 126, 142, 156, 147, 77, 248, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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