Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bcdf0e370d9e4a8b1104a78ddb2a3a8014063cb921d962ed61ae17a64826107

Tx prefix hash: f87b758a5e93561935aa81e63ed06e9e78453a19dbeafad6b36c70b79c48d891
Tx public key: c1049c1647a3301e54cc80eb128003dcd8db9c38caecf79bbee1d97f11438c8b
Timestamp: 1681365098 Timestamp [UCT]: 2023-04-13 05:51:38 Age [y:d:h:m:s]: 02:006:08:43:44
Block: 737484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526721 RingCT/type: yes/0
Extra: 01c1049c1647a3301e54cc80eb128003dcd8db9c38caecf79bbee1d97f11438c8b021100000001b3164c24000000000000000000

1 output(s) for total of 2.210088096000 dcy

stealth address amount amount idx
00: 412bf3d142738b77c0153cc3943d78cb99d20c3b4980df3fa493c6eb3e435e5d 2.210088096000 1184043 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": 737494, "vin": [ { "gen": { "height": 737484 } } ], "vout": [ { "amount": 2210088096, "target": { "key": "412bf3d142738b77c0153cc3943d78cb99d20c3b4980df3fa493c6eb3e435e5d" } } ], "extra": [ 1, 193, 4, 156, 22, 71, 163, 48, 30, 84, 204, 128, 235, 18, 128, 3, 220, 216, 219, 156, 56, 202, 236, 247, 155, 190, 225, 217, 127, 17, 67, 140, 139, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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