Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76fce6e32e62d5963f5b5c96949a318b2b5581ccb067b9e434dea7a2ade38213

Tx prefix hash: e0ccdd11ca7b50605a6edaa30ea44f1e4dad2b2d4e77974efeeb170f86c27eac
Tx public key: 86c5a196bec0ea0e9df80842c61aa6f65d70a031b9f52a8a3644420f70e4d3df
Timestamp: 1713096232 Timestamp [UCT]: 2024-04-14 12:03:52 Age [y:d:h:m:s]: 01:177:08:46:17
Block: 1000295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385393 RingCT/type: yes/0
Extra: 0186c5a196bec0ea0e9df80842c61aa6f65d70a031b9f52a8a3644420f70e4d3df02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ec18d4667588115773b42207d28c48fb5162c57144fd0e2e6b3521c80107c1d 0.600000000000 1460793 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": 1000305, "vin": [ { "gen": { "height": 1000295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ec18d4667588115773b42207d28c48fb5162c57144fd0e2e6b3521c80107c1d" } } ], "extra": [ 1, 134, 197, 161, 150, 190, 192, 234, 14, 157, 248, 8, 66, 198, 26, 166, 246, 93, 112, 160, 49, 185, 245, 42, 138, 54, 68, 66, 15, 112, 228, 211, 223, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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