Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b75c67dd4f999264795b11b7ed27e471e248f045bbc715d13baceef7a5586fee

Tx prefix hash: 3753c891381fb8d5b918cb80096e650edd9b8c031147d16bde8bd24dfab7305b
Tx public key: ea0d26aa29946cae69400fb1177a9cc00007392d834b53c73a0ec0ea4bd7e0a6
Timestamp: 1714411387 Timestamp [UCT]: 2024-04-29 17:23:07 Age [y:d:h:m:s]: 00:299:16:05:32
Block: 1011218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214187 RingCT/type: yes/0
Extra: 01ea0d26aa29946cae69400fb1177a9cc00007392d834b53c73a0ec0ea4bd7e0a60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bb11f0e047818a60d47f85854459f9f203d82656efcff0ef4f181ddf3c94f9b 0.600000000000 1473390 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": 1011228, "vin": [ { "gen": { "height": 1011218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bb11f0e047818a60d47f85854459f9f203d82656efcff0ef4f181ddf3c94f9b" } } ], "extra": [ 1, 234, 13, 38, 170, 41, 148, 108, 174, 105, 64, 15, 177, 23, 122, 156, 192, 0, 7, 57, 45, 131, 75, 83, 199, 58, 14, 192, 234, 75, 215, 224, 166, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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