Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec370291b9eec5cae11d27b758f62558a18d49045868ca16dc0136d81b11747e

Tx prefix hash: e31b45a96e33cb44f4a1a39d7cac397919801ff5de5441fae75940256f2bca68
Tx public key: 6fd0c0d2302758099a9a8d9723c466e54b287bfbc26e69f9b4773e26056475a1
Timestamp: 1721014258 Timestamp [UCT]: 2024-07-15 03:30:58 Age [y:d:h:m:s]: 00:269:07:35:36
Block: 1065976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192401 RingCT/type: yes/0
Extra: 016fd0c0d2302758099a9a8d9723c466e54b287bfbc26e69f9b4773e26056475a102110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9f75c0961ad64c1e41566f4edeec694aea42f78cfed4e33980b5b573bdfd8be 0.600000000000 1536545 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": 1065986, "vin": [ { "gen": { "height": 1065976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9f75c0961ad64c1e41566f4edeec694aea42f78cfed4e33980b5b573bdfd8be" } } ], "extra": [ 1, 111, 208, 192, 210, 48, 39, 88, 9, 154, 154, 141, 151, 35, 196, 102, 229, 75, 40, 123, 251, 194, 110, 105, 249, 180, 119, 62, 38, 5, 100, 117, 161, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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